-
-
EDITOR HOME
Performance Statistics
ST Interval
-
The Pro-Act software option enhances the unit's ability to collect performance information by giving it the capability to monitor (track) protocols and sockets for application layer Short Term and Long Term statistics.
-
-
Note:
This feature is only available if your unit contains Pro-Act software. For information on upgrading your unit on-site with the Pro-Act software option, see Upgrading with Pro-Act.
-
Long Term Statistics
-
Long-term statistics are collected on all Probes whether or not they contain the Pro-Act software. The only Long-term collection difference is that Pro-Act enables you to define up to eight protocol filters under the Configured Filters field. If Pro-Act is not installed, these filters are hard-coded to monitor only Layer 2 throughput statistics. Long Term Statistics are collected by monitoring the application PVCs These PVCs, identified by DLCI, may either be automatically identified by the unit or can be user-defined through the Frame Relay Performance configuration by DLCI name and/or number. For TFrap and SFrap, the maximum DLCIs that can be collected is 50. For DFrap and Frap, the maximum DLCIs that can be collected is 16.
-
Up to eight protocols may be selected from the Supported Protocols list and monitored. There are an additional four socket-level IP protocols which can also be tracked.
-
-
Note:
If you are unable to configure different protocols for each DLCI, all DLCIs will be monitored for the same protocols.
-
-
Long Term performance statistics are collected during a sampling interval. The sampling interval can be configured to vary in length (4 to 3600 seconds).
-
Short Term Statistics
-
Short Term Statistics are collected PVCs processed by the unit. For TFrap and SFrap, the maximum DLCIs that can be collected is 100. For DFrap and Frap, the maximum DLCIs that can be collected is 16. These statistics are based on protocols tracked by the unit. Short Term statistics are also collected on four user-defined TCP and UDP socket-level protocols. Short Term statistics are collected during a sampling interval. The sampling interval can be configured to vary in length (3 to 60 seconds). At the end of each interval, the statistics are transferred into memory for future viewing.
-
Unit is Pro Act Compatible
-
Enable this feature if the Pro-Act software option is installed on the unit. If disabled, all other fields will be ignored.
-
Protocols Supported
-
The protocols listed in this field reflect the protocols that are available to the unit for Short and Long-term statistical monitoring and tracking.
-
From this list, select a protocol you wish to support, then click on the Add button. To remove a protocol from the Configured Filters list, select the protocol you want to remove, then click on the Remove button.
-
Configured Filters
-
The protocols listed in this field reflect the contents of the Long-term protocol filter table. This table identifies which protocols will be monitored and tracked for Long-term statistics. Up to eight may be defined.
-
-
Note: To include a user-defined socket-level protocol for Long-term statistical collection, click on the ADD button, then transfer the user-defined filter (Tx and/or Rx) that matches the socket ID from the Protocols Supported field to the Configured Filters field. Unlike Short-term statistical collection, which monitors each DLCI for all protocol filters (including defined user ports <sockets>), Long-term statistics include only the DLCIs identified in the DLCI Configured Filters field for the matching protocol filters listed under the Protocols Configured Filters field. The DLCIs listed in this field reflect the contents of the Long-term DLCI table. This table identifies which DLCIs will be monitored and tracked for Long-term statistics. Unlike Short-term statistical collection, which monitors and tracks all detected DLCIs, Long-term statistics are only collected on user-defined virtual DLCI circuits.
-
Socket Addresses
-
This table enables you to assign TCP or UDP IP protocol filters to the unit's user ports (sockets).
-
Each socket address table entry contains an ID number and a single user-defined TCP or UDP socket-level IP protocol identifier.
-
The socket-level protocol filter supplements the filters that are already resident on the unit and provides additional Short and Long-term DLCI performance statistics. Transmit (Tx) and Receive (Rx) statistics are collected on the configured socket.
-
-
Note:
If two socket addresses identify the same protocol filter, statistics will only be collected from the socket which was assigned the first occurrence of the protocol. If a socket address identifies a protocol filter that is already being monitored or tracked by another unit filter, statistic counts collected from this socket will not be placed in the socket's "bucket". They are placed under the name of the actual protocol filter.
-
-
ID identifies the socket address's user-defined protocols table entry. The numbers listed in this field are used to index table entries and will only appear if there is a corresponding TCP/UDP protocol port entry.
-
-
TCP/UDP Port Number are the user-defined TCP and/or UDP socket-level IP protocols assigned to user ports (sockets). Entries are identified by ID. Protocols are identified in each field by a numerical value. A value setting of zero indicates a non-defined protocol for the corresponding socket.
-
DLCIs Supported
-
The DLCIs listed in this field reflect the DLCIs the unit detects and that are available for Long-term statistical monitoring and tracking.
-
ST Interval
-
Defines the Short Term sampling interval timer. This value determines the length of time for each Short-term collection interval. At the end of each interval, all "bucket" counts are transferred into the storage memory called Previous. When the transfer completes, current register counts are reset to zero and a new sampling cycle begins.
-
Range: 3 -- 60 seconds
-
LT Interval
-
Defines the Long Term sampling interval timer. This value determines the length of time for each Long-term collection interval. At the end of each interval, all "bucket" counts are moved into memory (up to 96 intervals may be stored). Once the transfer completes, register counts are reset to zero and a new sampling cycle begins. The length of each interval determines how many hours of statistics can be stored in memory. For example, to store 24 hours of Long-term statistical counts, configure each interval to equal 15 minutes (900 seconds).
-
Range: 4 -- 3600 seconds